Contact information updating via SMS

ABSTRACT

A source mobile telephone detects that a telephone number of the telephone has changed to a new number, and in response, sends a text or short message service (SMS) notice message to contacts identified in the mobile telephone to indicate that the source mobile telephone has a new telephone number. In response to receiving the text or SMS notice message, a contact telephony device may update its contact list to reflect the new number. Other embodiments are also described.

This application is a continuation of U.S. application Ser. No.12/270,798 filed on Nov. 13, 2008 now U.S. Pat. No. 8,170,588.

FIELD

Embodiments of the invention relate to a mobile phone sending text orshort message service (SMS) messages to contacts listed in the mobiletelephone to indicate that the mobile telephone has a new telephonenumber. Other embodiments are also described.

BACKGROUND

While continuing to grow in popularity, portable or mobile electronicdevices, such as cellular phones or mobile phones have also been growingin complexity. In addition to supporting wireless voice communication,mobile devices or phones, such as the iPhone™multifunction device byApple, Inc., of Santa Clara, Calif., include additional functionalitysuch as built-in digital photo and video camera, digital music and moviefile playback, self-location capability, and global positioning system(GPS).

Moreover, most mobile phones are configurable to allow a user tocustomize features such as the display background image, ring-tones,notification sounds, volume levels, and display brightness levels. Theycan also typically be customized to select which additionalfunctionalities to include, and to customize the features of thosefunctionalities. Moreover, mobile phones may be configurable to allow auser to program the phone with telephone contacts, and text (or shortmessage service (SMS)) message contacts. Mobile phones may also beconfigurable to allow a user to send, receive, take and/or store variousmedia in the phone, including text (or SMS) messages, photos, audiofiles (e.g., songs and voice recordings) and videos. Thus, a user maydesire and find more useful, a mobile phone configured to have thefeatures, customization, functionality, contacts, and media the usermost frequently uses.

When a mobile phone user travels or relocates, the user may want tochange phone services (e.g., phone service providers, such as to reducecalling costs, messaging costs, and/or other phone function costs, whilemaintaining the same mobile phone. For instance, when a user of a mobilephone travels, such as to a region or country where the user desires touse a different phone service, that user may replace the currentsubscriber identity module (SIM) card of the user's mobile phone with anew or different SIM card that provides service with the desired serviceprovider. Replacing the SIM card allows the user to retain thefunctionality, and customization of the user's current mobile phone,while using a different telephone service provider. Thus, by using ormaintaining his phone when traveling or relocating to different regionsor countries, a phone user may make more efficient use the functionalityof his phone, as compared to another phone, due to the users familiaritywith that device, while reducing costs for calling, messaging, and usingthe phone functionalities.

SUMMARY

In accordance with embodiments of the invention, a source mobiletelephone is able to detect that a telephone number of the telephone haschanged to a new number, and in response, is able send a notice messageto contacts identified in a contact list of the mobile telephone toindicate to the contact recipients that the sending mobile telephone hasanew telephone number.

For instance, replacing the SIM card of the user's phone may require themobile phone to have a different, new phone number and/or serviceprovider. The user's mobile phone contacts may not know that the user'sphone has a new phone number or service provider. An embodiment of theinvention alleviates such a situation by automatically modifying thosecontacts, of the user's new number.

The user may be prompted by his telephone to select amongst the contactsto be sent the messages. It may receive, from the user, selectionsidentifying the contact, such as from the contact list, Also, the sourcemobile telephone may prompt its user to indicate a period of time overwhich the new telephone number is to be in service, or a date and timeuntil which the new telephone number is to remain in service.

In some embodiments, upon detecting that the telephone number haschanged, the mobile telephone may automatically send the notice messagesto the contacts, without requiring explicit approval from the user foreach of the contacts.

In response to receiving the notice message, a contact telephony devicemay update its contact list to reflect the new number. The contacttelephony device may monitor such received notice messages anddistinguish them from other messages and notices.

The user of the contact telephony device may be prompted to accept thechange of source mobile telephone phone number.

In the case where the received notice message includes a selected periodof time or a selected date and time, the contact telephony device maydisplay to its user that the sending mobile telephone will have the newtelephone number over the selected period of time or until the selecteddate and time.

In some cases, the contact telephony device may revert back to theoriginal senders mobile telephone number after the selected period oftime or after the selected date and time. The user of the contacttelephony device may be prompted to accept the reversion back to theoriginal senders mobile telephone number after the selected period oftime, or after the selected date and time.

In some embodiments, upon or in response to receiving the noticemessage, contact telephony device may automatically to accept the changeof source mobile telephone phone number, and/or revert back to theoriginal senders mobile telephone number after the selected period oftime, or after the selected date and time, without prompting the contactuser to accept the change, or reversion back to the original sendersmobile telephone number.

Embodiments also include program instructions stored on a storage mediumand/or electronic circuitry to perform the functions and processesdescribed above.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments of the invention are illustrated by way of example andnot by way of limitation in the figures of the accompanying drawings inwhich like references indicate similar elements. It should be noted thatreferences to “an” or “one” embodiment of the invention in thisdisclosure are not necessarily to the same embodiment, and they mean atleast one.

FIG. 1 is flow diagram describing a process for detecting that atelephone number of a sender mobile telephone has changed, and aresponse to detecting, sending a contact change notice message tocontacts of the source mobile telephone.

FIG. 2 is a flow diagram describing a process of a contact telephonydevice receiving a message from a source mobile phone, and in response,updating a contact list of the contact telephony device to reflect thenew number for the sender mobile telephone.

FIG. 3 is a block diagram of a source mobile phone, contact telephonydevices, and messages sent by the source mobile phone to the contacttelephony devices.

DETAILED DESCRIPTION

Embodiments of the invention provide mobile phone users who change theirphone's contact information (e.g., service provider and/or phone number)a more efficient process for notifying their phone's contacts of the newnumber. For example, according to embodiments, a source mobile telephoneis able to detect that a telephone number of the telephone has changedto a new number, and in response, is able send a notice message tocontacts identified in a contact list of the mobile telephone toindicate to the contact recipients that the sending mobile telephone hasa new telephone number.

Embodiments also provide the contact with a more efficient process forupdating their contact list with the new number. For example, accordingto embodiments, in response to receiving the notice message, a contacttelephony device is able to update a contact list to reflect the newnumber.

For instance, a mobile phone user may want to change a phone number orservice of their mobile phone to correspond with or as a result ofchanging to a new job, a new residence, a new location, a new state, anew country or travel (e.g. travel to a new location, such as when auser buys a “China SIM” to insert into their cell phone for service inChina). The phone user may change or replace a mobile phone's subscriberidentity module (SIM) card (having the user's identification (ID),service provider information, and mobile phone number) with a differentSIM card (having the same user's identification, but a different serviceprovider information, and/or a different mobile phone number). Ifchanging the SIM card changes the phone's service and/or phone number,the user's contacts may not know of the change. Thus, it may benecessary for the user to notify the contacts of the user that the useris at a different telephone number, and/or is using a different phoneservice.

The notice messages or “messages” describedtherein may be any type oftext message or other data carried On channels or services such as shortmessage service (SMS). In some embodiments, the text messages mayinclude SMS text messages that are designed as part of GSM, or anothernetwork, such as a 3G network. The text messages may also include textmessages as part of non-GSM networks, E-mail messages from phones,standard mail protocol networks (such as SMTP over TCP/IP). It is alsoconsidered that the text messages may include contact cards, vCards andthe like, such as files or objects that can be passed instead of just“text messages”.

The processes, instructions and/or circuitry describedtherein may solvethe problem of notifying the contacts in the user's phone of the contactinformation change, without the time consuming process of calling, ormanually sending separate messages to each contact, and requiring eachcontact to go through the hassle of changing the number on their phoneonce notified. Moreover, the processes, instructions, or circuitrydescribedtherein will help the sender and receiver better manage thenumber change, by providing a more accurate “automated” change leadingto fewer number transcription errors during the change; and allowing thechange to revert back to the original number, at the appropriate time,if the change is not permanent (e.g., such as in the case of the ChinaSIM travel example).

FIG. 1 is flow diagram describing a process for detecting that atelephone number of a source or sender mobile telephone has changed anda response to detecting, sending a contact change notice message tocontacts of the source mobile telephone (e.g., to contacts listed in thesource mobile phone as having telephony devices). FIG. 1 shows process100 that may be implemented by program instructions stored on a storagemedium and/or electronic circuitry of a mobile telephone (e.g., a“source” or “sender” mobile phone), as describedtherein.

At block 110 a source mobile telephone detects that a telephone numberof the telephone has changed to a new number. For example, block 110 mayinclude a processor, SIM card interface, or circuitry of the phonedetecting the change, such as by comparing a phone number of a changed,new or replacement SIM card with that in a memory from the prior SIMcard, and detecting a difference or change in the number (e.g., a changein any one of the numbers of the total phone number, such as includingarea code, prefix and suffix). If the numbers are different, theprocessor, SIM card interface, or circuitry may send a change notice,including the new number, as noted at block 140.

It can be appreciated that a phone number, as describedtherein mayinclude all of the numbers of the total phone number required to call amobile phone (e.g., the source phone) or landline phone, such asincluding area code, prefix and suffix (e.g., for a United States ofAmerica (USA) number); or country code and all other required numbers tocall the source (e.g., for a Non-USA number).

In some embodiments, at block 120, the user may be prompted by thetelephone to select the contacts, such as from amongst a contact list ofthe phone, to be sent the messages. At block 120, the telephone may alsoreceive from the user selections identifying the contacts, such as fromthe contact list.

For example, a dialog may be displayed to the user, asking if the userwants to send an SMS update to “all or some” of the user's contactsstored in the phone? If the user selects “all”, then an SMS is sent toeach contact. If the user selects “some”, then the user may be promptedto select which contacts of the list to send a message to. It can beappreciated that all or some of the contacts send the messages may notbe in the phones contact list, but may be entered by the user, inresponse to prompting for “new” contacts to send a message to. Thisprompting may provide benefits of notice to the user of the change ofphone number notice messages, and selection of which contacts to notifyof the change and/or user's travel.

In some embodiments, at block 130, the source mobile may prompt the userto indicate a period of time over which to have the new telephone numberor a date and time until which to have the new telephone number. Forexample, a dialog may be displayed to the user, prompting the user toselect either “for how long” or “until when” the new number will beused, or neither? If the user selects “for how long” then a dialog maybe displayed prompting the user to indicate a period of time over whichthe new telephone number is to be in service. If the user selects “forhow long” then a dialog may be displayed prompting the user to select(e.g., from a calendar listing) or indicate a date time until which thenew telephone number is to remain in service. This prompting may providebenefits of notice to the user of sending the contacts the change ofphone number notice messages with the period of time, or date and timefor the end of the change, and/or end of the user's travel.

At blocks 120 and 130, a display (such as a touch screen) may be used toprompt the source user to select the contacts to be sent the messages, aperiod of time over which to have the new telephone number, and/or adate time until which to have the new telephone number. Also, an input,such as a touch screen or keypad may be used to receive inputs from theuser to select the contacts, period of time, and/or date and time.

In some embodiments, block 120 and/or block 130 may not occur or may notbe performed. For example, in some embodiments, upon detecting that thetelephone number has changed, the mobile telephone may “automatically”send the notice messages to the contacts without prompting the user toselect the contacts, to indicate a period of time, or to select (orindicate) a time and date as noted above. In this case, referring backto block 110, if the numbers are different, the processor, SIM cardinterface, or circuitry may automatically send a change notice as notedat block 140 without prompting the user and without requiring explicitapproval from the user for each of the contacts.

At block 140, in response, to detecting, the source phone sends a changenotice message (e.g., a “notice message”) to contacts identified in acontact list of the mobile telephone to indicate to the contactrecipients that the sending mobile telephone has a new telephone number.One message may be sent to each of the contacts to indicate the newnumber or phone number change. Each notice message sent to each of thecontacts may be a message addressed only to that one contact (e.g., to asingle phone number or URL). Alternatively, each notice may be a messageaddressed to all of the contacts that notification messages are sent to.The message may be sent based on possible prompting, selecting, orautomatically as noted above. In some cases it is only necessary to sendone message to make the change and a reversion (see below). However, inother cases, more than one message may be sent to make the change and areversion.

For example, block 140 may include a processor, transmitter, orcircuitry of the phone sending a separate notice message to eachcontacts identified in a contact list, or selected by the user toindicate to the contact recipients that the sending mobile telephone hasa new telephone number. For example, the message may notify to eachcontact that the sending mobile telephone has a new telephone number(such as by including the sending phone user ID) and identify what thatnew phone number is.

The notice message may include message data or headers having apredetermined code that identifies the message as a contact changenotice message, and the new phone number (e.g., see block 110).Specifically, the notice message with new contact information (e.g.including the new phone number, and also the source user or sourcemobile phone identification) may be sent in a message that isspecifically formatted, such as by including a header (e.g., see header331 of FIG. 3) indicating that the message is a “Contact InformationChange” message (e.g. the header may specify “Contact InformationChange”). Each message may include the period of time, or to select atime and date selected above at block 130. It can be appreciated that abenefit of the source phone having detecting and sending capability isbeing able to send multiple messages to update the source phone numberat multiple contacts without having to take the time or effort to make aseparate or individual call or notify each contact.

FIG. 2 is a flow diagram describing a process of a contact or receivertelephony device (e.g., a mobile or landline (elephone) receiving anotice message from a source mobile phone, and in response, updating acontact list of the contact telephony device to reflect the new numberfor the sender mobile telephone (e.g., the receiver telephony device mayhave the source phone listed in its contact list as having a mobilephone).

FIG. 2 shows process 200 that may be implemented by program instructionsstored on a storage medium and/or electronic circuitry of a telephonydevice (e.g., a “contact” or “receiver” mobile phone capable device, orlandline phone capable device), as describedtherein. FIG. 2 showsprocess 200 that may be implemented by program instructions stored on astorage medium and/or electronic circuitry of a mobile telephone (e.g.,a “contact” or “receiver” telephony device), as describedtherein. FIG. 2may be a process that occurs as a result of a telephony device receivingthe notice message sent in block 140 of FIG. 1.

At block 210, in response to receiving the notice message at a contacttelephony device indicating that a number of the source mobile telephonehas changed to a new number. For example, a contact device may receive amessage notifying the device that the sending mobile telephone has a newtelephone number (such as by including the sending phone user ID) andidentifying what that new phone number is.

For example, block 210 may include a processor, receiver, or circuitryof the device monitoring received messages including the contact changenotice message and other notices; and distinguishing or detecting thechange notice message from other messages and notices. In accordancewith embodiments, the processor, receiver, or circuitry may detect thechange by comparing the received message data or headers to apredetermined code that identifies a message as a contact change noticemessage. For example, a specially formatted notice message having newcontact information (e.g. a new source phone number, and also includinga source user or mobile phone identification) may be detected bydetecting the message has a header (e.g., see header 331 of FIG. 3)indicating “Contact Information Change” (e.g. such as by the headerstating that the message is a “Contact Information Change” message). Ifa notice message is detected the processor, receiver, or circuitry mayupdate a contacts list of the contact device to include or reflect thenew number provided in the notice message as noted at block 240. In somecases, “other” messages and notices may include TV voting, productpromotion, advertisement, quiz, spam, political campaign, social, work,non-phone related, and other non-phone number change messages andnotices.

In some embodiments, at block 220, the user of the contact telephonydevice may be prompted by the telephony device to accept the change ofsource mobile telephone phone number. At block 220, the telephony devicemay also receive from the contact user, selections identifying acceptingthe change, such as to update or include the new number in a contactlist of the telephony device. For example, a dialog may be displayed tothe contact user, asking if the user wants to accept the new number toupdate a contact of the user's contact list stored in the device? If theuser selects “yes”, then the contact is updated. In some embodiments, ifthe source user or source phone is not listed in the devices contactlist, the contact user may be prompted to add a “new” contact to thelist having the new number and source user as the contact. Thisprompting may provide benefits of notice to the contact user of thechange of phone number, and possibly of the source user's travel.

In some embodiments, in the case where the notice message includes anindicated period of time or a selected (or indicated) date and time(e.g., see block 130), at block 230 the contact telephony device maydisplay to its user (e.g., using a dialog displayed to the user) thatthe sending mobile telephone will have the new telephone number over theindicated period of time, or until the selected (or indicated) date andtime. This displaying may provide benefits of notice to the contact userof the period of time, or date and time for the end of the change,and/or end of the source user's travel.

Also, in some embodiments, at block 230, the contact device may promptthe contact user to accept “selected automatic” or “prompted” reversionto the original phone number, after the selected period of time or atthe selected date and time. For example, a dialog may be displayed tothe user, prompting the user to select either “selected automatic” or“prompted” reversion, or “neither”? If “selected automatic” reversion isselected at block 230, then selected automatic reversion may occur asdiscussed further below at block 250. If “prompted” reversion isselected at block 230, then prompted reversion may occur as discussedfurther below at block 250. If “neither” is selected at block 230, thenreversion may not occur as discussed further below at block 250.

At block 240, the contact telephony device may update a contact list toreflect the new number for the source mobile telephone. Block 240 maydescribe the contact telephony device being able to or performing anupdate of a contact list in response to receiving the notice message.Updating may also be based on possible prompting, selecting (e.g., seeblocks 220 and/or 230), or fully automatically as noted herein.Reflecting the new number may include updating, changing replacing aprior phone number in a contact list of the contact device, for thesource user or mobile phone. The new number may then be included in thecontact list (e.g., all of the numbers of the total phone number areacode, prefix and suffix).

For example, block 240 may include a processor, receiver, or circuitryof the device updating a contact identified in a contact list, orselected by the user, with the new number provided in the noticemessage. The new number may be reverted back to the prior number afterthe period of time, or to select a time and date noted above at block230.

In some embodiments, block 220 and/or block 230 may not occur or may notbe performed. For example, in some embodiments, upon or in response toreceiving the notice message, the contact telephony device may“automatically” accept the change of source mobile telephone phonenumber without prompting the contact user to accept the change. In thiscase, referring back to block 210, if the notice is detected, theprocessor, receiver, or circuitry may automatically accept and make thechange to the contact list as noted at block 240 without prompting theuser at block 220 or block 230.

At block 250, in some embodiments, the contact telephony device mayrevert back to the original senders mobile telephone number after theindicated period of time, or after the selected (or indicated) date andtime received in the notice message from the source phone. In somecases, at block 250, the contact device may prompt the contact user whenreverting back to the original senders mobile telephone number after theindicated period of time, or after the selected (or indicated) date andtime, without prompting the contact user to accept the change, orreversion back to the original senders mobile telephone number. Thisprompting may provide benefits of notice or of a reminder to the contactuser that the period of time, or date and time of the number change,and/or source user's travel has ended.

For example, if “selected automatic” reversion is selected at block 230,then selected automatic reversion may occur without further displayingor prompting the contact user, at the time of reversion, about thereversion. If “prompted” reversion is selected at block 230, thenprompted reversion may occur by displaying to the contact user, at thetime of reversion, that the reversion is going to occur. Promptedreversion may include the contact user selecting (e.g., by dialog andselection) not to revert the new number to the original number. If“neither” is selected at block 230, then reversion may not occur, at thetime of reversion.

At blocks 220, 230 and 250, a display (such as a touch screen may beused to display information and to prompt the contact user to makeselections noted for those blocks. Also, an input, such as a touchscreen or keypad may be used to receive inputs from the contact user tomake selections noted for those blocks.

At block 250, in some embodiments, upon or in response to receiving thenotice message, the contact telephony device may “fully automatically”revert back to the original senders mobile telephone number after theindicated period, of time or after the selected (or indicated) date andtime, without displaying or prompting the contact user about thereversion. In this case, referring back to block 210, if the notice isdetected, the processor, receiver, or circuitry may fully automaticallyrevert to the prior number and make the change to the contact list asnoted at block 250 without prompting the user at block 230. It can beappreciated that an advantage of the processes describedtherein is areduction in half of the amount of message traffic required to updatethe contact lists of contact devices to the new phone number and revertthem back to the prior phone number. For example, if “selectedautomatic” reversion or “fully automatic” reversion is used, it is notnecessary for the source phone to send another message to the contactphone to cause the reversion to occur (e.g., the change message needonly be sent once).

Alternatively, if the phone number of the source phone is changed backto the original or prior number, without reversion (or if it is changedto another number), another notice message with the new contactinformation (e.g. the new phone number) may be sent in a subsequentmessage to the contact device(s). That is, FIG. 1 may be repeated tosend a subsequent message to revert to the prior number, the sourcephone number, back to the prior number at contact devices of contacts ofthe source phone.

Additional benefits of the contact phone having receiving and updatingcapabilities, include a contact user being able to update one (ormultiple) contacts of the device's contact list with new phone numbers,for one or various) periods of time, with reduced user effort andreduced error. For example, the contact user does not need to thinkabout or write down each new phone number, or possibly when they will beused until. Also, the contact user will know each source user is using adifferent service and new number, and can avoid calling, texting,sending photos, or sending videos to the source user if the new numberor different service will increase the costs of the call, texting,sending photos, or sending videos as compared to the prior number orservice.

It is considered that more than one message (e.g., ten or more messages)may be received by contact device from various source phones to indicatethe new numbers or phone number changes. In these cases, the benefitsabove will be multiplied by the number of messages received. Forinstance, a contact user's device will be able to accurately andefficiently detect and update (and may revert) phone number changes forten or more source notice messages received by the contact device fromvarious source phones that are using new or changed numbers during anoverlapping time period. It can be appreciated that a benefit of thecontact phone having receiving and updating capability (and possiblychanging numbers for a received time period, such as until a receiveddate and time), will reduce user effort, confusion and errors inaccurately and timely changing multiple contact phone numbers.

In some embodiments, for telephony devices that do not have updatingcapability, the contact user may make the contact list change manually,such as by writing down the new number; cut and paste (or block andcopy) the number, or using a menu structure of the device. In this case,the source user still realized benefits noted above for FIG. 1, and thecontact user realized benefits of knowing the source user is using adifferent service and new number, and can avoid calling the source userif the new number or different service will increase the costs of thecall, as compared to the prior number or service.

The blocks of process 100 and 200 may be performed sequentially in theorder shown, with the exception that any one or more of blocks 120, 130,220, 230, and 250 may be omitted form those processes. In someembodiments, only blocks 110 and 140 of process 100 will be performed.In some embodiments, only blocks 210 and 240 of process 200 will beperformed.

Embodiments may include software application instructions stored in astorage medium (e.g. a machine-readable medium) that when executed by aprocessor cause the processor (e.g. a machine such as a mobile phone,telephony device, and the like) to perform some or all of the operationsdescribedtherein (e.g., see FIG. 1 and/or FIG. 2) (e.g. cause some orall of the processes describedtherein to be performed by the machine). Amachine-readable medium may include any mechanism for storinginformation in a form readable by a machine (e.g., a computer), such asa Compact Disc Read-Only Memory (CD-ROM), Read-Only Memory (ROM), RandomAccess Memory (RAM), USB memory device, and/or Erasable ProgrammableRead-Only Memory (EPROM).

In other embodiments, some of these operations might be performed byspecific hardware components that contain hardwired logic. Suchembodiments include various electronic circuitry, such as electronichardware, logic, processors, transistors, resistors, inductors,capacitors, registers, processors, memory, signal traces, other hardwaredescribedtherein (e.g., see FIG. 3) and the like to perform thefunctions and processes described herein. Those operations mightalternatively be performed by any combination of software applicationinstructions components and hardware components.

FIG. 3 is a block diagram of network 300 including a source mobile phone310, contact telephony devices 340, 360, and 380, and messages 330, 332,and 334 sent by the source mobile phone to the contact telephonydevices. Network 300 may be a wireless telephony network, or may be anetwork that includes a wireless telephony network, as well as othernetwork types as further noted below. Mobile phone 310 and contacttelephony devices 340, 360, and 380, may be configurable to allow a userto input or program them with telephone contacts (e.g., including usercontact identification (ID); and mobile and/or landline phone numbers),and/or message contacts (e.g., including user contact identification(ID); and phone numbers and/or email addresses). A user may perform suchinputting or programming by using a display and input of the phone ordevice.

Embodiments of the invention include a source or sender mobile telephone310 having memory 304 to store contact list 320, user identification 324(e.g. identifying the source user and/or phone 310), and new phonenumber 326. Memory 304 may also include the original, old, or priorphone number 325 for phone 310, such as for comparison with new phonenumber 326 as noted above. Contact list 320 includes contacts 322 suchas user identifications and phone numbers of the contacts of contactlist 320 which may include user identification and/or phone numbers forphone 340, 360, and 380. Memory 304 may be a mobile phone memory orcomputer memory (e.g., a main memory) as know in the industry, such asRead-Only Memory (ROM), Random Access Memory (RAM), and/or ErasableProgrammable Read-Only Memory (EPROM).

Display 306 known in the industry, such as by being apart of a graphicaluser interface (GUI). A display 306 (such as a touch screen) may also beused to prompt the source user to select the contacts to be sent themessages, a period of time over which to have the new telephone number,and/or a date time until which to have the new telephone number, such asnoted above for FIGS. 1 and 2.

Input 308 may be an input as known in the industry. Input 308 may bepart of a GUI, such as by working with display 306 to provide GUIfunctionality. Input 308 may be an input, such as a touch screen orkeypad may be used to receive inputs from the user to select thecontacts, period of time, and/or date and time.

Phone 310 also includes SIM card interface 328, such as includingcircuitry and a plug-in connector for receiving and removably attachinga SIM card. SIM card 329 is show physically and electronically attachedto interface 328. SIM card 329 may include new phone number 326 and userID 324.

In some embodiments, new phone number 326, stored in memory 304, is adifferent phone number than the original or prior phone number 325 ofphone 310 stored in memory 304. New phone number 326 and may be thephone number stored in SIM card 329. New phone number 326 and user ID324 may be received from card 329 by phone 310, memory 304, and/orprocessor 302, such as for comparison with the prior phone number andfor inclusion in notice messages.

Phone 310 also includes processor 302 coupled to memory 304, interface328, input 308, display 306, and transmitter 312. Processor 302 may be acomputer processor or microprocessor as known in the mobile phone and/orcomputer industry. Processor 302 may be a processor to, upon detectingthe telephone number change, such as by comparing phone number 326 to anoriginal phone number stored in memory 304, send a notice message, suchas sending one or more of notice messages 330, 332 and 334, usingtransmitter 312. A message (e.g., such as message 330) may be sent toall or some of contacts 322, by sending a message to phone numbers ortext message addresses identified in contacts 322.

New phone number 326 and user ID 324 received from SIM card 329 by phone310 may be compared (e.g., by processor 302) with prior phone number 325of phone 310 stored in memory 304 (and an original or prior user IDsphone 310, which may be the same as user ID 324) to detect or identifyif number 326 is a new phone number 326 received from card 329. If it isdifferent, then the source telephony device (e.g., caused by processor302) may send a message to contacts, such as sending one or more ofnotice messages 330, 332 and 334, using transmitter 312 (e.g., see block140 of FIG. 1). If the numbers are the same, or if the original or prioruser IDs phone 310 is different than user ID 324, phone 310 may not senda notification message.

Embodiments of the invention also include a contact or receivertelephony device 340 having receiver 352 to receive the notice message330 from transmitter 312. Memory 344 is coupled to receiver 352 to storecontact list 352 of the contact telephony device 340. Contact list 354includes contacts 356, and may be a list including a different contactuser identification (e.g. including user identification (ID) 324) and adifferent contact phone number 357 (e.g. including prior or originalphone number for phone 310) for each contact of contacts 356. Memory 344may be a mobile phone or computer memory (e.g., a main memory) as knowin the industry, such as Read-Only Memory (ROM), Random Access Memory(RAM), and/or Erasable Programmable Read-Only Memory (EPROM).

Phone 340 includes display 346, which may be a display as known in theindustry. Display 346 may be part of a GUI display 346 (such as a touchscreen) may be made to prompt the contact user to accept the change ofsource mobile telephone phone number 326such as noted above for FIGS. 1and 2.

Input 348 may be an input as known in the industry. Input 348 may bepart of a GUI, such as by working with display 346 to provide GUIfunctionality. Input 348 may be an input, such as a touch screen orkeypad may be used to receive inputs from the contact user to accept thechange of source mobile telephone phone number, as noted above for FIGS.1 and 2.

Phone 340 also includes SIM card interface 359, which may be aninterface such as described above for interface 328. Phone 340 is alsoshown including SIM card 358, which may be a card similar to thatdescribed above for card 329, except for having the user identificationand phone number for phone 340.

Phone 340 also includes processor 342, such as a computer processor ormicroprocessor as known in the industry for a mobile phone, telephonydevice or computer. Processor 342 may be a processor to, in response toreceiving notice message 330, update contact list 354 of the contacttelephony device to reflect the new number 326, such as noted above forFIGS. 1 and 2.

In some embodiments, new phone number 326, received in message 330 byphone 340 is a different phone number than the prior or original phonenumber of phone 310, which may be stored in memory 334 (e.g., stored incontact list 354 at the contact of contacts 356 having user ID 324). Newphone number 326 and user ID 324 may be received in message 330 by phone340 and compared with user IDs of contacts 356 to determine or identifythe contact of contacts 356 having user ID 324. Once the contact havingID 324 is identified, new phone number 326 received in message 330 maybe compared with the prior or original phone number of phone 310, todetermine or identify whether new phone number 326 is different than theprior or original phone number of phone 310. If it is different, thenthe contact telephony device may update the contact list having user ID324 to reflect the new number for the source mobile telephone (e.g., seeblock 240 of FIG. 2). If the numbers are the same, phone 340 may notupdate the contact list having user ID 324.

Alternatively, in some embodiments, once the contact having ID 324 isidentified, the contact telephony device will update the contact listhaving user ID 324 to reflect the new number for the source mobiletelephone, regardless of whether the phone numbers are different. Inthis case, the contact telephony device may save battery life andcomputing power by performing the update without comparing the phonenumbers.

In some embodiments, even if a contact having ID 324 is not identified,new phone number 326 received in message 330 may be used to update thecontact list, such as by creating a contact having user ID 324 and thenew number for the source mobile telephone (e.g., see block 240 of FIG.2).

Finally, the contact telephony device 340 may include signal processingcircuitry to monitor received messages to distinguish the notice messagefrom other notices and messages, such as by monitoring message headersto detect or identify a header indicating that the message is a “ContactInformation Change” message (e.g. the header may specify “ContactInformation Change”). This signal processing circuitry may be part ofprocessor 342 or separate circuitry couple to processor 342.

Phones 360 and 380 may have components that correspond to thosedescribed above for phone 340. However, each of SIM card 358, 378, and398 will have a unique user identification and telephone number. Asnoted above for FIGS. 1 and 2, contact list 354, 374, and/or 394 mayinclude the user identification and original or prior phone number forphone 310. However, in some cases, one or all of those lists may nothave user ID 324 and the prior phone number of phone 310 (e.g such as inthe case where the user of the contact telephony device has not yetentered phone 310 into the devices contact list).

Arrows 314, 315 and 316 are show to represent transmitter 312 sendingmessages 330, 332, and 334, respectively, such as using network 300(e.g., including a wireless telephony network). Likewise, arrows 337,338, and 339 are show to represent receivers 352, 372, and 392 receivingmessages 330, 332, and 334 respectively, such as using network 300(e.g., including a wireless telephony network). Messages 330, 332, and334 may include header 331, such as a header indicating that the messageis a “Contact Information Change” message (e.g. the header may specify“Contact Information Change”). Messages 330, 332, and 334 may alsoinclude user identification (ID) 324, which may identifies the user asthe same user and/or identifies the phone as phone 310. In addition,messages 330, 332, and 334 include new phone number 326, which may be adifferent phone number than the prior or original phone number 325 ofphone 310 and may be the phone number stored in SIM card 329 (andreceived from card 329 by phone 310, memory 304, and/or processor 302).In some embodiments, each message may include the period of time; or atime and date, as noted above at block 130.

It is contemplated, that messages 330, 332, and 334 may be sent over awireless telephony network that may be combined with othercommunications networks, capable of sending text and/or SMS messages.Specifically, it is considered that phone 310, 340, 360, and 380 may beany of various mobile phones known in the art capable of sending andreceiving tcxt or SMS messages.

The wireless telephony network (e.g. included in network 300) may be inaccordance with known cellular telephone communication network protocolsincluding, for example, global system for mobile communications, GSM,enhanced data rate for GSM evolution, EDGE, and worldwideinteroperability for microwave access, WiMAX. In some embodiments, thenetwork may include a 3G network, a non-GSM network, standard mailprotocols such as SMTP over TCP/IP,” and/or networks that supportcontact cards, vCards, files or objects. Thus, mobile phone 310 anddevices 340, 360, and 380 may have a subscriber identity module, SIM,card, which is a detachable smart card that contains the subscriptioninformation of its user (e.g. user ID 324 for phone 340), and may alsocontain a contacts list of the user (e.g. list 320 for phone 310).

Mobile phone 310 and devices 340, 360, and 380 may be made of a housingwithin which are integrated several components including those describedabove, as well as a receiver (earpiece speaker), a microphone(mouthpiece), a speakerphone, and a vibration actuator. Additionalcircuitry, including a combination of hardware circuitry and software,are, of course, included to obtain the needed functionalitydescribedtherein. These are not described in detail as they would bereadily apparent to those of ordinary skill in the art of mobile phonecircuits and software. It is sufficient to appreciate that the mobilephone telephony or devices include a processor and circuitry (e.g. atelephone module) which is responsible for coordinating various tasksduring a call. The telephone module may be one or more pieces ofsoftware or firmware, to coordinate tasks such as dialing a call,directing audio signals during the call (between the microphone and thecalled party and between the called party and the receiver orspeakerphone), and ending the call.

A user or caller of source phone or contact device may own the mobilephone or device, or may otherwise be its primary user. The phone ordevice may be assigned a unique address by a wireless telephony networkoperator (e.g., service provider), such as an eleven-digit internationaltelephone number or an Internet Protocol, IP, address.

Any of contact devices 340, 360 and/or 380, may be a mobile phone, orinstead may be a land-based device that is coupled to a telephonynetwork through wires or cables. Each of contact devices 340, 360 and/or380 may also be identified with a unique address, such as a telephonenumber within the public switched telephone network. The contact devices340, 360 and/or 380 may also have an Internet protocol (IP) address ifit performs calls through a voice over IP (VOIP) protocol. The contactdevices 340, 360 and/or 380 may thus be a cellular handset, a plain oldtelephone service, POTS, analog telephone, a VOIP telephone station, ora desktop or notebook computer running telephony software.

As noted above, embodiments may include machine accessible medium storedon a storage medium such as a CD, DVD, USB memory device or other mediumthat store program instructions, that when executed, cause a machine orprocessor (e.g., of a mobile phone and/or telephony device) to performthe functions and processes describedtherein. This storage medium may beincluded in, accessible by, read by, or used to program memory 304and/or another memory accessible by processor 302 to executeinstructions to perform processes described above for FIG. 1. Similarly,such a storage medium may be accessible by memory 344, 364, and 384and/or another memory accessible by processor 302 to executeinstructions to perform processes described above for FIG. 2.

The processes, instructions, and circuitry herein may be designed and/orsold by handset manufacturers, such as manufacturers of a “sourcedevice” that sends a notice when its phone number has been changed;and/or a “contact” device or a recipient device that receives the noticeof the phone number change.

The invention is not limited to the specific embodiments describedabove. For example, although source contact information has beendescribed in the context of updating a source phone number, the conceptis applicable to updating other contact information of a contactlisting, such as a personal or job email address, phone serviceprovider, or a residence or job street address, such as in response to achange of residence, phone service provider, email address, or job. Inthis situation, the notice message (e.g. message 330, 332, and 334) mayinclude a new email address and/or a new street address, in place of thephone number (e.g. in place of phone number 320, but the message willalso still include user ID 324 and header 331). Accordingly, otherembodiments are within the scope of the claims.

What is claimed is:
 1. A machine-implemented method in a mobiletelephone, comprising: the mobile telephone detecting that a telephonenumber of the mobile telephone has chanced from a first telephone numberto a new telephone number; and in response to said detecting, the mobiletelephone sending a contact change notice message to each of a pluralityof contacts identified in a contacts list of the mobile telephone,wherein the message indicates to its recipient that the mobile telephonehas the new telephone number over a finite indicated period of time oruntil an indicated date and time; and after sending the contact changenotice message, the mobile telephone sending another contact changenotice message, to each of the plurality or contacts, to indicate to itsrecipients that the mobile telephone has reverted back to the firsttelephone number prior to at least one of the finite indicated period oftime or the indicated date and time.
 2. The method of claim 1, whereinsending comprises: prompting a user of the mobile telephone that sendsthe contact change notice message to indicate one of a finite period oftime over which to have the new telephone number, and a date and timeuntil which to have the new telephone number prior to sending thecontact change notice message.
 3. The method of claim 1, wherein sendingcomprises: prompting a user to select the plurality of contacts to besent the contact change notice message; and receiving user selectionsidentifying the plurality of contacts of the user from the contact list.4. The method of claim 1, wherein sending comprises the mobile telephoneautomatically sending a text or SMS contact change notice withoutprompting the user to identify the contacts.
 5. A machine-implementedmethod in a telephony device, comprising: the telephony device g achange notice message from mobile telephone, wherein the messageindicates that a number of the mobile telephone has changed from a firsttelephone number to a new number; and in response to said receiving, thetelephony device updating a contacts list of the telephony device toreflect the new number for said mobile telephone, wherein the receivedmessage indicates to its recipient that the mobile telephone will havethe new telephone number over a finite indicated period of time or untilan indicated date and time; and reverting back to the first telephonenumber prior to the finite indicated period of time and prior to theindicated date and time received in the contact change notice message inresponse to another contact change notice message from the mobiletelephone.
 6. The method of claim 5, wherein updating comprises thetelephony device that received the message displaying to a user of thetelephony device, the finite indicated period of time or the indicateddate and time received in the contact change notice message.
 7. Themethod of claim 5, wherein updating comprises the telephony deviceprompting a user of the telephony device to accept the update.
 8. Themethod of claim 5, wherein receiving comprises the telephony device:monitoring received messages including the contact change notice messageand other messages; distinguishing the contact change notice messagefrom the other messages; and automatically updating the contacts listwithout prompting a user of the telephony device to accept the update.9. A mobile telephone comprising: a memory to store a contacts list anda mobile telephone number; a processing system coupled to the memory,the processing system to, upon detecting that the telephone number ofthe mobile telephone has changed from a first telephone number to a newtelephone number send a contact change notice message to each of aplurality of contacts identified in the contacts list, wherein themessage indicates to its recipient that the mobile telephone has the newtelephone number over a finite indicated period of time or until anindicated date and time, and the processor to send, after sending thecontact change notice message, another contact change notice message toeach of the plurality of contacts to indicate to its recipients that themobile telephone has reverted back to first telephone number prior to atleast one of the finite indicated period of time or the indicated dateand time.
 10. The mobile telephone of claim 9, further comprising aninput to prompt a user of the mobile telephone that sends the contactchange notice message to indicate a finite period of time over which tohave the new telephone number, or a date and time until which to havethe new telephone number prior to sending the contact change noticemessage.
 11. The mobile telephone of claim 9, further comprising aninput to prompt a user to select the plurality of contacts to be sentthe contact change notice message from the contact list, and to receiveuser selections identifying the contacts from the contact list.
 12. Themobile telephone of claim 9, wherein the memory stores a user identity;and further comprising: an interface coupled to the processor, theinterface detachably coupled to a subscriber identity module (SIM) cardstoring the user identity and the new mobile telephone number.
 13. Amachine readable non-transitory storage medium storing executableinstructions which when executed perform a method in a mobile telephone,the method comprising: the mobile telephone detecting that a telephonenumber of the mobile telephone has changed from a first telephone numberto a new telephone number; and in response to said detecting, the mobiletelephone sending a contact change notice message to each of a pluralityof contacts identified in a contacts list of the mobile telephone,wherein the message indicates to its recipient that the mobile telephonehas the new telephone number over a finite indicated period of time oruntil an indicated date and time; and after sending the contact changenotice message, the mobile telephone sending another contact changenotice message, to each of the plurality of contacts, indicate to itsrecipients that the mobile telephone has reverted back to the firsttelephone number prior to at least one of the finite indicated period oftime or the indicated date and time.
 14. The medium of claim 13, whereinsending comprises: prompting a user of the mobile telephone that sendsthe contact change notice message to indicate one of a finite period oftime over which to have the new telephone number, and a date and timeuntil which to have the new telephone number prior to sending thecontact change notice message.
 15. The medium of claim 13, whereinsending comprises: prompting a user to select the plurality of contactsto be sent the contact change notice message; and receiving userselections identifying the plurality of contacts of the user from thecontact list.
 16. The medium of claim 13, wherein sending comprises themobile telephone automatically sending a text or SMS contact changenotice without prompting the user to identify the contacts.
 17. Amachine readable non-transitory storage medium storing executableinstructions which when executed perform a method in a telephony device,the method comprising: the telephony device receiving a contact changenotice message from a mobile telephone, wherein the message indicatesthat a number of the mobile telephone has changed from a first telephonenumber to a new number; and in response to said receiving, the telephonydevice updating a contacts list of the telephony device to reflect thenew number for said mobile telephone, wherein the received messageindicates to its recipient that the mobile telephone will have the newtelephone number over a finite indicated period of time or until anindicated date and time; and reverting back to the first telephonenumber prior to the finite indicated period of time and prior to theindicated date and time received in the contact change notice message inresponse to another contact change notice message from the mobiletelephone.
 18. The medium if claim 17, wherein updating comprises thetelephony device that received the message displaying to a user of thetelephony device, the finite indicated period of time or the indicateddate and time received in the contact change notice message.
 19. Themedium of claim 17, wherein updating comprises the telephony deviceprompting a user of the telephony device to accept the update.
 20. Themedium of claim 17, wherein receiving comprises the telephony device:monitoring received messages including the contact change notice messageand other messages; distinguishing the contact change notice messagefrom the other messages; and automatically updating the contacts listwithout prompting a user of the telephony device to accept the update.